The lifecycle event tracker — install/update detection, cold-launch
sequencing, foreground/background transitions, and the one-shot
deep-link buffer. Standalone class; not yet wired into
MetaRouterAnalyticsClient (slice 3 does the wiring).

Cold-launch decision tree:
- no persisted state, no identity → Application Installed
- no persisted state, identity present → Application Updated with
  previous_version/previous_build = 'unknown' (SDK upgrade)
- persisted (version, build) matches → no install/update event
- persisted (version, build) differs → Application Updated with prior
  values

Cold-launch Opened ordering depends on the foreground-state probe:
- foreground at SDK init → emit Opened immediately and suppress the
  imminent ProcessLifecycleOwner.onStart so we don't double-emit
- background at SDK init (silent push, JobScheduler, WorkManager) →
  defer Opened to the first true ON_START transition, which then emits
  with from_background=false as the cold-launch bridge

Deep-link buffer is one-shot and last-write-wins. Multiple openURL
calls before the next Opened keep only the most recent URL; the buffer
clears once attached to an Opened payload.

The tracker has no on/off switch — when the feature is disabled the
host (LifecycleCoordinator, slice 3) simply never constructs an
instance. AppContext is injected (the cached snapshot from slice 1)
so the tracker never reads PackageManager itself.

Refs: sc-38234

Three follow-ups from code review on slice 2.

- defaultForegroundCheck: narrow the catch from Throwable to
  IllegalStateException + NoClassDefFoundError. The wide catch swallowed
  OOM / StackOverflowError silently. ProcessLifecycleOwner.get() throws
  ISE off the main thread; the lifecycle-process artifact may be
  stripped in test setups, hence NoClassDefFoundError. Anything else
  surfaces as a real bug.
- onSdkReady: AtomicBoolean idempotency guard. If the host accidentally
  invokes the cold-launch sequence twice (future re-init path, test
  misuse) we used to re-emit Installed/Updated/Opened and stomp
  suppressNextForeground, which would eat the next legitimate foreground
  transition.
- KDoc: openURL / handleDeepLink reference said EXTRA_REFERRER goes
  through getStringExtra. Per Android docs EXTRA_REFERRER is a Uri, not
  a String — getStringExtra on it is essentially always null. Point
  hosts at Activity.referrer?.host instead.
- Tests cover the new idempotency guard and the onForeground-before-
  onSdkReady contract (documenting what happens if the host wiring
  invariant breaks).

Refs: sc-38234

End-to-end integration of the lifecycle subsystem. After this slice the
feature is fully functional behind `InitOptions.trackLifecycleEvents`
— default stays false so existing customers are not affected on
upgrade.

Coordinator seam
- LifecycleCoordinator wraps LifecycleEventTracker. MetaRouterAnalytics-
  Client no longer references the tracker directly; future session /
  attribution work has a clear place to land alongside lifecycle events.
- Constructed only when trackLifecycleEvents=true. When the feature is
  off, lifecycleCoordinator is null and every dispatch site is a
  null-safe no-op.

AppContext caching
- AnalyticsClient reads AppContext.fromContext() exactly once at init
  and injects the same snapshot into both DeviceContextProvider and
  LifecycleEventTracker. The per-event enrichment path no longer hits
  PackageManager.

Public API
- handleDeepLink renamed to openURL across AnalyticsInterface,
  AnalyticsProxy, PendingCall, and the proxied call replay. Name
  matches Segment's iOS SDK and avoids the over-promise of 'handle'
  (the SDK does not route or parse the URL — it buffers it for the
  next Application Opened).
- openURL on the client logs Logger.warn and no-ops when the feature
  is disabled. Silent no-op was bad DX; misconfiguration is now
  diagnosable from logcat.

Opt-in default
- InitOptions.trackLifecycleEvents flips from true to false. KDoc
  updated. InitOptionsTest renamed to assert the new default.

Lifecycle ordering
- onBackground emits Application Backgrounded BEFORE flush /
  flushToDisk so the event lands in the same drain (unchanged behavior;
  comment kept next to the code).

Refs: sc-38235

Slice 3 follow-ups from code review.

- onForeground ordering: dispatcher.resume() now runs BEFORE
  coordinator.onForeground(). Mirrors iOS so the resumed dispatcher
  picks up the just-emitted Application Opened in its next tick rather
  than waiting for the following flush cycle. Functionally benign on
  Android (track() enqueues regardless of dispatcher state) but the
  cross-platform parity contract was an explicit constraint.
- Coordinator gate: trackLifecycleEvents is now the sole on/off signal.
  Previously a test seam injection of injectedLifecycleCoordinator could
  install a coordinator while the flag was false. Production paths were
  fine via MetaRouter.kt, but the off-state should be structurally
  enforced regardless of the seam.
- AnalyticsInterface.openURL KDoc: drop the misleading
  Intent.EXTRA_REFERRER + getStringExtra suggestion. Per Android docs
  EXTRA_REFERRER is a Uri (returns null via getStringExtra). Point hosts
  at Activity.referrer?.host, which is the canonical API for the
  calling-app host.
- DeviceContextProvider: KDoc on the appContext constructor default
  noting it exists for test ergonomics only. Production code must pass
  the explicit cached snapshot.

Refs: sc-38235

Slice 4 follow-ups from code review.

- Activity entry-point snippet: drop the misleading
  intent.getStringExtra(Intent.EXTRA_REFERRER) suggestion. EXTRA_REFERRER
  is documented as a Uri, not a String, so the String overload always
  returns null. Use Activity.referrer?.host (the canonical API) instead.
- Add an explicit imports block to the Activity snippet so it's
  copy-paste-runnable.
- Soften intent.data!! in the privacy sample to a guarded let — a
  privacy-themed example shouldn't crash on a bare bang.
- Add the android.net.Uri import to the sanitize() snippet for the same
  reason.

Refs: sc-38236